Feature/yash/caching #173
Open
Feature/yash/caching #173
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Tracking Info
Resolves #168
Changes
What changes did you make?
Added caching for user info on the frontend so that user info is still available even when network is down. Also uses cached info instead of sending a new request each time even when the network is up.
(TODO - Sessions caching)
Testing
How did you confirm your changes worked?
Tested pages with server not running.
Confirmation of Change
Upload a screenshot, if possible. Otherwise, please provide instructions on how to see the change.
Login and load the profile page at least once with the server running. Switch to another page. Then stop the server and switch to the profile page again - this switch should work fine with all the information showing as normal.